Method and system for displaying a position of a vehicle at a remotely located device

ABSTRACT

A system and method includes a mobile device having a mobile device identifier associated therewith and an in-vehicle infotainment system. The mobile device communicates the mobile device identifier to the in-vehicle infotainment system. A user device is controllable by inputs from a user though a user interface display associated with the user interface. A global positioning system generates a vehicle position signal at the vehicle. The user device is separate from the in-vehicle infotainment system and the global positioning system. The in-vehicle infotainment system communicates the vehicle position signal corresponding to a current vehicle position and the mobile device identifier to the user device. The user device is associated with a display displaying a map display comprising a map with a representation of the vehicle at the current vehicle position and the mobile device identifier of the mobile device.

RELATED APPLICATIONS

The application is a continuation of the U.S. patent application Ser.No. 14/983,231 filed on Dec. 29, 2015. The disclosure of the aboveapplication is incorporated herein by reference.

TECHNICAL FIELD

The present disclosure relates generally locating system and, morespecifically, to a method and system for displaying the location of auser identifier.

BACKGROUND

The statements in this section merely provide background informationrelated to the present disclosure and may not constitute prior art.

Television programming content providers are increasingly providing awide variety of content to consumers. Available content is typicallydisplayed to the user using a grid guide. The grid guide typicallyincludes channels and timeslots as well as programming information foreach information timeslot. The programming information may include thecontent title and other identifiers such as actor information and thelike.

Providing convenient ways for users to select and find content is usefulto content providers. Mobile phones are have been used to order contentand watch content. Wearable devices such as computer watches and headmounted computers are increasing in popularity. Utilizing such devicesin the control of content would increase customer satisfaction.

SUMMARY

The present disclosure provides a system and method for displaying avehicle location on a user device. The user device may be a mobiledevice or a wearable device. The user device may also be a set top box.

In one aspect of the disclosure, a method includes coupling a mobiledevice having an identifier to an in-vehicle infotainment system,generating a vehicle position signal for a vehicle, communicating theidentifier and the vehicle position signal corresponding to a currentvehicle position to a user device, the user device separate from themobile device and the in-vehicle infotainment system, the user devicecontrollable by inputs from a user through a user interface displayassociated with a user interface and generating a map display at theuser device, the map display displaying a map comprising arepresentation of the vehicle at the current vehicle position and theidentifier of the mobile device.

In a further aspect of the disclosure, a system includes a mobile devicehaving a mobile device identifier associated therewith and an in-vehicleinfotainment system. The mobile device communicates the mobile deviceidentifier to the in-vehicle infotainment system. A user device iscoupled to the in-vehicle infotainment system of a vehicle. The userdevice is controllable by inputs from a user though a user interfacedisplay associated with the user interface. A global positioning systemgenerates a vehicle position signal at the vehicle. The user device isseparate from the in-vehicle infotainment system and the globalpositioning system. The in-vehicle infotainment system communicates thevehicle position signal corresponding to a current vehicle position andthe mobile device identifier to the user device. The user device isassociated with a display displaying a map display comprising a map witha representation of the vehicle at the current vehicle position and themobile device identifier of the mobile device.

In yet another aspect of the disclosure, a method includes coupling amobile device having an identifier to an in-vehicle infotainment system,generating a vehicle position signal at a vehicle, communicating thevehicle position signal corresponding to a current vehicle position to auser device set top box, the set top box separate from the mobile deviceand the in-vehicle infotainment system, the set top box controllable byinputs from a user though a user interface display associated with theuser interface, communicating the identifier to the user device set topbox from the in-vehicle infotainment system, and enabling the set topbox user device to generate a map display comprising a representation ofthe vehicle at the current vehicle position and the identifier of themobile device.

Further areas of applicability will become apparent from the descriptionprovided herein. It should be understood that the description andspecific examples are intended for purposes of illustration only and arenot intended to limit the scope of the present disclosure.

DRAWINGS

The drawings described herein are for illustration purposes only and arenot intended to limit the scope of the present disclosure in any way.

FIG. 1 is a block diagrammatic view of a communication system accordingto one example of the present disclosure.

FIG. 2 is a block diagrammatic view of a user receiving device accordingto one example of the present disclosure.

FIG. 3 is a block diagram of a head end according to one example of thepresent disclosure.

FIG. 4A is a block diagram of a mobile device according to one exampleof the present disclosure.

FIG. 4B is a block diagram of the audio addition module of FIG. 4A.

FIG. 5 is a block diagram of a wearable device according to one exampleof the present disclosure.

FIG. 6 is a high level block diagrammatic view of an in-vehicleinfotainment system.

FIG. 7 is a flowchart of a method for resuming playback of contentplayed through the vehicle.

FIG. 8A is a screen display for resuming content.

FIG. 8B is a screen display for resuming the playback of content.

FIG. 9 is a flowchart of a method for recording a suggestion orreminder.

FIG. 10A is a screen display illustrating a reminder displaying tuningand recording buttons.

FIG. 10B is a screen display confirming a signal being sent to a set topbox.

FIG. 10C is a screen display tuning to content being streamed.

FIG. 11 is a flowchart of a method for tracking the position of avehicle.

FIG. 12A is a screen display for making a voice-over-IP call to avehicle.

FIG. 12B is a screen display for calling to a set top box.

FIG. 13 is a screen display for displaying cameras from within thevehicle.

FIG. 14 is a screen display illustrating a travelled map of the vehicle.

FIG. 15 is a flowchart of a method for storing a position of a vehicle.

FIG. 16A is a screen display displaying a parked position query todetermine whether a user would like to determine the parked location ofthe vehicle.

FIG. 16B is a screen display illustrating a map with a parked positionof the vehicle.

FIG. 17 is a flowchart of a method for operating the in-vehicleinfotainment system according to user profiles.

FIG. 18A is a block diagrammatic view of screen displays coupled to thein-vehicle infotainment system having various displays.

FIG. 18B illustrates screen displays with a primary display controllingthe secondary displays.

FIG. 19 is a flowchart of a method for operating different screendisplays according to user profiles.

FIG. 20 is a screen display illustrating content available that wascommunicated from a set top box.

FIG. 21 is a flowchart of a method displaying different portions of acontent signal.

FIG. 22 is a screen display for the screens with an in-vehicleinfotainment system having different portions of the content signaldisplayed at different devices.

FIG. 23 is a flowchart of a method for operating an in-vehicleinfotainment system using a broadcasted audio-video signal and playingback the enhanced audio signal at an in-vehicle infotainment system.

FIG. 24 shows screen displays at a mobile device and at an in-vehicleinfotainment system that plays back an enhanced audio stream.

DETAILED DESCRIPTION

The following description is merely exemplary in nature and is notintended to limit the present disclosure, application, or uses. Forpurposes of clarity, the same reference numbers will be used in thedrawings to identify similar elements. As used herein, the term modulerefers to an application specific integrated circuit (ASIC), anelectronic circuit, a processor (shared, dedicated, or group) and memorythat execute one or more software or firmware programs, a combinationallogic circuit, and/or other suitable components that provide thedescribed functionality. As used herein, the phrase at least one of A,B, and C should be construed to mean a logical (A or B or C), using anon-exclusive logical OR. It should be understood that steps within amethod may be executed in different order without altering theprinciples of the present disclosure.

The teachings of the present disclosure can be implemented in a systemfor electronically communicating content to an end user or user device.Both the data source and the user device may be formed using a generalcomputing device having a memory or other data storage for incoming andoutgoing data. The memory may comprise but is not limited to a harddrive, FLASH, RAM, PROM, EEPROM, ROM phase-change memory or otherdiscrete memory components.

Each general purpose computing device may be implemented electronicallyin analog circuitry, digital circuitry or combinations thereof. Further,the computing device may include a microprocessor or microcontrollerthat performs instructions to carry out the steps performed by thevarious system components.

A content or service provider is also described. A content or serviceprovider is a provider of data to the end user. The service provider,for example, may provide data corresponding to the content such asmetadata as well as the actual content in a data stream or signal. Thecontent or service provider may include a general purpose computingdevice, communication components, network interfaces and otherassociated circuitry to allow communication with various other devicesin the system.

Further, while the following disclosure is made with respect to thedelivery of video (e.g., television (TV), movies, music videos, etc.),it should be understood that the systems and methods disclosed hereincould also be used for delivery of any media content type, for example,audio, music, data files, web pages, advertising, etc. Additionally,throughout this disclosure reference is made to data, content,information, programs, movie trailers, movies, advertising, assets,video data, etc., however, it will be readily apparent to persons ofordinary skill in the art that these terms are substantially equivalentin reference to the example systems and/or methods disclosed herein. Asused herein, the term title will be used to refer to, for example, amovie itself and not the name of the movie. While the followingdisclosure is made with respect to example DIRECTV® broadcast servicesand systems, it should be understood that many other delivery systemsare readily applicable to disclosed systems and methods. Such systemsinclude wireless terrestrial distribution systems, wired or cabledistribution systems, cable television distribution systems, Ultra HighFrequency (UHF)/Very High Frequency (VHF) radio frequency systems orother terrestrial broadcast systems (e.g., Multi-channel Multi-pointDistribution System (MMDS), Local Multi-point Distribution System(LMDS), etc.), Internet-based distribution systems, cellulardistribution systems, power-line broadcast systems, any point-to-pointand/or multicast Internet Protocol (IP) delivery network, and fiberoptic networks. Further, the different functions collectively allocatedamong a service provider and integrated receiver/decoders (IRDs) asdescribed below can be reallocated as desired without departing from theintended scope of the present patent.

Referring now to FIG. 1, a satellite television broadcasting system 10is illustrated. The satellite television broadcast system 10 includes ahead end 12 that generates wireless signals 13 through an antenna 14which are received by an antenna 16 of a satellite 18. The wirelesssignals 13, for example, may be digital. The wireless signals 13 may bereferred to as an uplink signal. A transmitting antenna 20 generatesdownlink signals 26 that are directed to a user receiving device 22. Theuser receiving device 22 may be located within a building 28 such as ahome, multi-unit dwelling or business. The user receiving device 22 isin communication with an antenna 24. The antenna 24 receives downlinksignals 26 from the transmitting antenna 20 of the satellite 18. Thus,the user receiving device 22 may be referred to as a satellitetelevision receiving device. However, the system has applicability innon-satellite applications such as a wired or wireless terrestrialsystem. For example, broadband wired or optical systems may benefit fromthe teachings set forth herein. Therefore the user receiving device 22may be referred to as a television receiving device, set top box, homemedia center or home gateway. More than one user receiving device 22 maybe included within a system or within a building 28. The user receivingdevices 22 may be interconnected.

The user receiving device 22 may be in communication with a router 30that forms a local area network 32 with a mobile device 34 and awearable device 36. The router 30 may be a wireless router or a wiredrouter or a combination of the two. For example, the user receivingdevice 22 may be wired to the router 30 and wirelessly coupled to themobile device 34 and to the wearable device 36. The router 30 maycommunicate internet protocol (IP) signals to the user receiving device22. The IP signals may be used for controlling various functions of theuser receiving device 22. IP signals may also originate from the userreceiving device 22 for communication to other devices such as themobile device 34 or the wearable device 36 through the router 30. Themobile device 34 and the wearable device 36 may also communicate signalsto the user receiving device 22 through the router 30.

The router 30 may be open, in which any device can communicatetherewith, or password protected, so that a password must be providedfrom a device before the router can be used.

The mobile device 34 may be, but is not limited to, a mobile phone,tablet computer, laptop computer or any other type of computing device.The mobile device is not fixedly connected to wires. The wearable device36 is one specific type of mobile device.

The wearable device 36 may be one of a number of types of wearabledevices that are worn by a user. The wearable device 36 may be fixedwearable by a user meaning it is meant to be affixed to the user.Examples of wearable devices 36 include a computerized watch such as aMicrosoft®, Samsung® or Apple® watch. The watch devices are fixed to anarm of the user. Another example of the wearable device 36 is GOOGLEGLASS® which is fixed to a head of a user. Of course, other types ofwearable devices affixed to other parts of the body may be used. Thewearable device 36 may be in direct communication with the userreceiving device 22 and the mobile device 34 through a Bluetooth®connection. The wearable device 36 may also be in communication with theuser receiving device 22 and the mobile device 34 through an IPconnection through the router 30. The wearable device 36 may also be incommunication with devices outside the local area network 32 through therouter 30. That is, the wearable device 36 may communicate with otherdevices such as the head end 12 through the network 50. The wearabledevice 36 may also be in communication with the mobile device 34 whichprovides a bridge or a communication path to the router 30 andultimately to the user receiving device 22 or the network 50. Thewearable device 36 may generate signals such as selection signals thatare communicated through the mobile device 34 but are destined to beused by the user receiving device 22, the head end 12 or other userdevices in communication with the network 50.

The mobile device 34 may also be in communication with the router 30,the head end 12 and various other devices through the network 50 orother devices in other parts of the network.

The user receiving device 22 includes a screen display 38 associatedtherewith. The display 38 may be a television or other type of monitor.The display 38 may display both video signals and audio signals.

The mobile device 34 may also have a display 40 associated therewith.The display 40 may also display video and audio signals. The display 40may be integrated into the mobile device 34. The display 40 may also bea touch screen that acts as at least one user interface. Other types ofuser interfaces on the mobile devices may include buttons and switches.

The wearable device 36 may also have a display 42 associated therewith.The display 42 may also display video and audio signals. The display 42may be integrated into the wearable device 36. A projected display oruser interface may also be projected on a surface adjacent to the eye ofa user. The display 42 may also be a touch screen that acts as at leastone user interface such as in a wearable watch type device. The device36 may display function selectors or “buttons” that are other types ofuser interfaces on the wearable devices may include buttons andswitches.

The user receiving device 22 may be in communication with the head end12 through an external network or simply, network 50. The network 50 maybe one type of network or multiple types of networks. The network 50may, for example, be a public switched telephone network, the internet,a mobile telephone network or other type of network. The network 50 maybe in communication with the user receiving device 22 through the router30. The network 50 may also be in communication with the mobile device34 through the router 30. Of course, the network 50 may be in directcommunication with the mobile device 34 or wearable device 36 such as ina cellular system.

An in-vehicle infotainment system 44 may be incorporated into a vehicle46. The in-vehicle infotainment system 44 may include an antenna 48 forcommunicating with the network 50. The in-vehicle infotainment system 44may also be in communication with a router 30 when in range thereof. Aswill be described below, when the in-vehicle infotainment system 44 iswithin the range of a router 30 associated with the customer's account,synchronization of various data may take place. That is, the router 30and the in-vehicle infotainment system 44 may belong to the same user.Identifiers or passwords may be exchanged to verify the in-vehicleinfotainment system 44 and to allow inter-communications may take place.The antenna 48 may be used for communicating with the router 30, thenetwork 50 and may even be used to communicate with the satellite 18. Ingeneral, the in-vehicle infotainment system 44 may be used by customerswith wearable devices or mobile devices within the vehicle, and thein-vehicle infotainment system 44 may act as an interface. As will bedescribed below, one or more displays 49 may be associated with thein-vehicle infotainment system. The display 49 may be used fordisplaying video signals, audio signals, or both.

The system 10 may also include a content provider 54 that providescontent to the head end 12. Although only one content provider 54 isillustrated, more than one content provider may be used. The head end 12is used for distributing the content through the satellite 18 or thenetwork 50 to the user receiving device 22, mobile device 34, thewearable device 36, or mobile device 44. The content provided may bevideo and or audio content, data such as metadata that relates to thecontent, and a content identifier. The content data may include lyricsfor use in a karaoke-type system described below. The lyrics are usefulfor audio content.

A data provider 56 may also provide data to the head end 12. The dataprovider 56 may provide various types of data such as schedule data ormetadata. The metadata may ultimately be provided to a user devicethrough the program guide system. The metadata may include variousdescriptions, actor, director, star ratings, titles, user ratings,television or motion picture parental guidance ratings, descriptions,related descriptions and various other types of data. The data provider56 may provide the data directly to the head end and may also providedata to various devices such as the mobile device 34, wearable device36, mobile device 34 and the user receiving device 22 through thenetwork 50. This may be performed in a direct manner through the network50.

The system 10 may also include an advertisement (ad) source 58. Theadvertisement source 58 provides advertisements through the network 50to the various devices such as the user receiving device 22, thewearable device 36 and the in-vehicle infotainment system 44. Theadvertisement source 58 may also communicate advertisements to the headend 12, where they may be broadcasted through the satellite 18. The adsources 58 may also be communicated from the head end 12 in apoint-to-point manner through the network 50.

Referring now to FIG. 2, a user receiving device 22, such as a set topbox is illustrated in further detail. Although, a particularconfiguration of the user receiving device 22 is illustrated, it ismerely representative of various electronic devices with an internalcontroller used as a content receiving device. Each of the componentsillustrated may be capable of communicating therebetween even though aphysical line is not drawn.

The antenna 24 may be one of a number of different types of antennasthat includes one or more low noise blocks. The antenna 24 may be asingle antenna 24 used for satellite television reception. The userreceiving device 22 is in communication with the display 38. The display110 may have an output driver 112 within the user receiving device 22.

A controller 114 may be a general processor such as a microprocessorthat cooperates with control software. The controller 114 may be used tocoordinate and control the various functions of the user receivingdevice 22. These functions may include a tuner 120, a demodulator 122,and a decoder 124 such as a forward error correction decoder, a bufferor other functions. The controller 114 may also be used to controlvarious function of the user receiving device 22.

The controller 114 may also include one or more of a language processingmodule 115, a command generation module 116, a language responsivenessmodule 117 and set-top box HTTP export functionality (SHEF) processormodule 118. Each of these modules is an optional feature of the userreceiving device 22. As will be described below the functions associatedwith each of the modules 115-118 may be performed in the user receivingdevice or one of the other devices such as the head end or the mobiledevice or a combination of the three. The modules 115-118 may be locatedremotely from each other and may also be stand-alone devices or vendorson the network 50. In general, the language processing module 115converts electrical signals that correspond to audible signals into atextual format or textual signal. The command generation module 116determines a user receiving device control command that corresponds withthe textual signal. The language responsiveness module 117 is used totrain the system to recognize various commands.

The SHEF processor module 118 is used to receive SHEF commands andtranslate the SHEF commands into actual control signals within the userreceiving device. Various types of SHEF commands for controlling variousaspects of the user receiving device may be performed. The SHEFprocessor module 118 translates the hypertext transfer protocol signalsreceived through the network into control signals within the userreceiving device 22.

The tuner 120 receives the signal or data from the individual channel.The tuner 120 may receive television programming content, program guidedata or other types of data. The demodulator 122 demodulates the signalor data to form a demodulated signal or data. The decoder 124 decodesthe demodulated signal to form decoded data or a decoded signal. Thecontroller 114 may be similar to that found in current DIRECTV® set topboxes which uses a chip-based multifunctional controller. Although onlyone tuner 120, one demodulator 122 and one decoder 124 are illustrated,multiple tuners, demodulators and decoders may be provided within asingle user receiving device 22.

The controller 114 is in communication with a memory 130. The memory 130is illustrated as a single box with multiple boxes therein. The memory130 may actually be a plurality of different types of memory includingthe hard drive, a flash drive and various other types of memory. Thedifferent boxes represented in the memory 130 may be other types ofmemory or sections of different types of memory. The memory 130 may benon-volatile memory or volatile memory.

The memory 130 may include storage for content data and variousoperational data collected during operation of the user receiving device22. The memory 130 may also include advanced program guide (APG) data.The program guide data may include various amounts of data including twoor more weeks of program guide data. The program guide data may becommunicated in various manners including through the satellite 18 ofFIG. 1. The program guide data may include a content or programidentifiers, and various data objects corresponding thereto. The programguide may include program characteristics for each program content. Theprogram characteristic may include ratings, categories, actor, director,writer, content identifier and producer data. The data may also includevarious user profiles such as other settings like parental controls.

The memory 130 may also include a digital video recorder. The digitalvideo recorder 132 may be a hard drive, flash drive, or other memorydevice. A record of the content stored in the digital video recorder 132is a playlist. The playlist may be stored in the DVR 132 or a separatememory as illustrated. The playlist may be a list of content stored inthe memory 130. The playlist may be general for all users or may be userspecific. The memory may also store user-specific settings such asfavorite channels, screen display data such as colors and font types,genres and music preferences.

The user receiving device 22 may include a voice converter such as amicrophone 140 in communication with the controller 114. The microphone140 receives audible signals and converts the audible signals intocorresponding electrical signals. Typically, this is done through theuse of a transducer or the like. The electrical signal corresponding tothe audible may be communicated to the controller 114. The microphone140 is an optional feature and may not be included in some examples aswill be described in detail below. The electrical signal may also beprocess in a remotely located language processing module. Thus, thecontroller 114 may convert the electrical signal into a “.wav” file orother suitable file type suitable for communication through a network50.

The user receiving device 22 may also include a user interface 150. Theuser interface 150 may be various types or combinations of various typesof user interfaces such as but not limited to a keyboard, push buttons,a touch screen or a remote control. The user interface 150 may be usedto select a channel, select various information, change the volume,change the display appearance, or other functions. The user interface150 may be used for generating a selection signal for selecting contentor data on the display 40.

A network interface 152 may be included within the user receiving device22 to communicate various data through the network 50 illustrated above.The network interface 152 may be a WiFi, WiMax, WiMax mobile, wireless,cellular, or other types of communication systems. The network interface152 may use various protocols for communication therethrough including,but not limited to, hypertext transfer protocol (HTTP). The networkinterface 152 may also be used to communicate through the router 30 ofFIG. 1 to the in-vehicle infotainment system 44. Various types of datawithin the user receiving device 22 may be communicated through thenetwork interface 152. For example, the network interface may obtain aplaylist or content associated with a playlist. The playlist may be alist of content stored within the memory 132 of the user receivingdevice for later playback. The playlist may be a general playlist forall users, or may be a specific playlist for each individual user. Thenetwork interface 152 may also communicate user settings such asfavorite channels, parental controls, font type and color schemes, tothe in-vehicle infotainment system.

A Bluetooth® module 154 may send and receive Bluetooth® signals to orfrom the mobile device or wearable device. The Bluetooth® signals may becontent or control signals.

A remote control device 160 may be used as a user interface forcommunicating control signals to the user receiving device 22. Theremote control device may include a keypad 162 for generating keysignals that are communicated to the user receiving device 22. Theremote control device may also include a microphone 164 used forreceiving an audible signal and converting the audible signal to anelectrical signal. The electrical signal may be communicated to the userreceiving device 22.

The user receiving device 22 may also include a profile manager 170. Theprofile manager 170 may use various profiles for operating andgenerating displays of the user receiving device. For example, the userreceiving device 22 may have various users associated therewith. Eachuser may have user data such as a profile that is used to operate thedevice to provide a customized user experience. The profiles may be usedto set various operations of the user receiving device 22 such as, butnot limited to, a list of favorite channels, a list of operationalsettings of the user receiving device, a recorded program playlist, andrecommendation characteristics. The recommendation characteristics maybe stored while the user is associated with the user receiving device bytuning or recording various programming. User profiles may be changed inresponse to the user's actions at the user receiving device 22. The usersettings may be established for the language, the parental controls, andother user established settings. By storing any user establishedsettings or adjustments, a profile can easily configure the userreceiving device and provide a consistent user experience without theuser having to provide inputs by scrolling through various menus at eachtelevision watching experience.

The profile manager module 170 may receive the various user data orprofiles that are stored within the memory 130. The user profiles mayalso be stored within the head end and communicated to the userreceiving device. A new user may have a user profile or user datacommunicated from the head end or always communicated from the head endwhen the user is identified to the user receiving device. As will bementioned below, the user may be identified to the user receiving device22 through a user identifier such as a numerical code, a user name, oran identifier associated with a mobile or wearable user receivingdevice.

A reminder module 172 may also be included within the controller of theuser receiving device 22. The reminder module 172 may be associated witha time clock or other device for generating a reminder set by a user. Areminder is a signal used for reminding a user that content is startingto be broadcasted or is about to be broadcasted. The reminder module 172may generate a screen display on the display 38 or generate a signalcommunicated to the mobile device 34, the wearable device 36 orin-vehicle infotainment system 44 that corresponds to the reminder. Thereminder display may provide various choices, such as record thecontent, or tune to the content. The recording or storing the contentmay take place at the device displaying the reminder or another device.

Referring now to FIG. 3, the head end 12 is illustrated in furtherdetail. The head end 12 may include various modules forintercommunicating with the mobile device 34, wearable device 36, thein-vehicle infotainment system 44 and the user receiving device 22illustrated in FIG. 1. Only a limited number of interconnections of themodules are illustrated in the head end 12 for drawing simplicity. Otherinterconnections may, of course, be present in a constructed example.The head end 12 receives content from the content provider 54 andadvertisements from the advertisement source 58 illustrated in FIG. 1. Acontent processing 310 processes the content for communication throughthe satellite 18. The content processing system 310 may communicate livecontent as well as recorded content. The content processing system 310may be coupled to a content repository 312 for storing content therein.The content repository 312 may store and process On-Demand orPay-Per-View content for distribution at various times. The Pay-Per-Viewcontent may be broadcasted in a linear fashion (at a predetermined timeaccording to a predetermined schedule). Linear content is presentlybroadcasting and may also be scheduled in the future. The contentrepository 312 may also store On-Demand content therein. On-Demandcontent is content that is broadcasted at the request of a userreceiving device and may occur at any time (not on a predeterminedschedule). On-Demand content is referred to as non-linear content.

The head end 12 also includes a program data module 313 that may includevarious types of data related to programming past, present and future. Aprogram guide module 314 may also be included in the program data module313. The program guide module 314 may include the programming data forpresent and future program data. The program data module may includedata for currently unavailable content. The currently unavailablecontent may be made available in the future. The program guide module314 communicates program guide data to the user receiving device 22illustrated in FIG. 1. The program guide module 314 may create variousobjects that are communicated with various types of data therein. Theprogram guide module 314 may, for example, include schedule data,various types of descriptions for the content and content identifierthat uniquely identifies each content item. The program guide module314, in a typical system, communicates up to two weeks of advanced guidedata for linear content to the user receiving devices. The guide dataincludes tuning data such as time of broadcast, end time, channel, andtransponder to name a few. Guide data may also include content availableon-demand and pay-per-view content. The program data module 33 may alsobe a web service that communicates program guide data to the mobiledevice 34 into the in-vehicle infotainment system 44.

An authentication module 316 may be used to authenticate various userreceiving devices, mobile devices and wearable devices that communicatewith the head end 12. The authentication module 316 may be incommunication with a billing module 318. The billing module 318 mayprovide data as to subscriptions and various authorizations suitable forthe user receiving devices, the mobile devices and wearable devices thatinteract with the head end 12. The authentication module 316 ultimatelypermits the user receiving devices and mobile devices to communicatewith the head end 12. Authentication may be performed by providing auser identifier, a password, a user device identifier or combinationsthereof.

A search module 320 may also be included within the head end 12. Thesearch module 320 may receive a search query comprising one or moresearch terms from various devices such as a mobile device or userreceiving device. The search module 320 may communicate search resultsto at least one of the user receiving device or the mobile device. Thesearch module 320 may interface with the program guide module 314 or thecontent processing system 310 or both to determine search result data.The search results may be personalized according to personal profiles,user data and viewing habits.

The head end 12 may also include a language processing module 330. Thelanguage processing module 330 may be used to generate text signals fromelectrical signals that correspond to audible signals received throughthe network 50 from a mobile device 34 or user receiving device 22illustrated in FIG. 1. The language processing module 330 may also be orinclude a voice converter. The language processing module 330 maycommunicate the text signals to a command generation module 332. Thecommand generation module 332 generates a user receiving device controlcommand that corresponds to the textual signal generated by the languageprocessing module 330. The command generation module may include variousvariations that correspond to a particular command. That is, peoplespeak in various ways throughout the country and various regions.Accents and other language anomalies may be taken into considerationwithin the command generation module 332. Details of this will bedescribed further below.

The head end 12 may also include a language responsiveness module 334that is used to improve the responsiveness of the language processingmodule 330 and the command generation module 332. The languageresponsiveness module 334 is a learning mechanism used to recognizevarious synonyms for various commands and associate various synonymswith various commands. The details of the language responsiveness module334 will be described in greater detail below.

The head end 12 may also include a recording request generator module340. Various signals may be communicated from a mobile device 34,wearable device 36 or the in-vehicle infotainment system 44 illustratedin FIG. 1, or another network type computing device. A request togenerate a recording may be communicated to the head end 12 andultimately communicated to the user receiving device 22. The recordingrequest may include a user receiving device identifier and a time toinitiate recording. Other data that may be included in the recordingrequest may include a channel, a transponder, a start time, an end time,a content delivery network identifier such as an IP address and variousother types of identifiers that allow the user receiving device 22 totune and record the desired content. The recording request generatormodule 340 may generate the record request in response to the reminderdisplay.

The head end 12 may also include a dialog manager 342. The dialogmanager 342 is used to generate a corrected text response such as asentence in response to a search request. The corrected text responsemay be a grammatically corrected text response. The grammaticallycorrect text response may be based on a classification that is derivedfrom the received text of the original audible signal. The grammaticallycorrect text response may also be provided in a voice signal that may beplayed back at the receiving device. An audible signal may be useful ina mobile device where text may not easily be reviewed without beingdistracted from other tasks like driving.

The head end 12 may also include a text generation module 344. The textgeneration module 344 may be used to generate text signals that arecommunicated through the network to the in-vehicle infotainment system44, the mobile device 34, or the wearable device 36. The text generationmodule 344 may, for example, provide a textual description of aparticular play in a football game or the like. The data may becommunicated from the text generation module 344 as a separate signalthat travels with the original signal. The textual signal may also becommunicated using an HTTP command through the network 50, illustratedin FIG. 1.

The head end 12 may include a profile processing module 350. The profileprocessing module 350 may receive a user identifier, a device identifieror both to identify a user. The user experience of a wearable device ora set top box may be changed based upon the characteristics of a user.The profile processing module 350 may provide user characteristics to aset top box or other user receiving device 22 through the network. Theprofile processing module 350 may store various types of data, includinga favorite channel list, a playlist and parental settings. The profileprocessing module 350 may also store identifiers corresponding tocontent watched so that recommendations may be provided to the user. Ascontent is watched, the content identifier and the user identifier maybe communicated to the head end and stored therein. Recommendations maythus be generated for a particular user that corresponds to content ofinterest to the user. The head end 12 may thus store profile data oruser data for all of the system users so that it may be distributed tovarious devices when necessary.

The recommendations may be generated in a recommendation module 352 bycomparing metadata associated with watched content or user profile toupcoming broadcasted content or available on-demand content. Therecommendations for a user may be communicated as a reminder signal anda reminder screen display.

The search module 320, the language processing module 330, the commandgeneration module 332, the language responsiveness module 334, thedialog manager 342, the text generation module 344 and the profileprocessing module 350 are illustrated by way of example for conveniencewithin the head end 12. As those skilled in the art will recognize,these modules 320-352 may also be located in various other locationstogether or remote to/from each other including outside the head end 12.The network 50 may be used to communicate with modules 320-352 locatedoutside the head end 12.

A content delivery network 354 may be in communication with a contentrepository 312. The content delivery network 354 is illustrated outsideof the head end 12. However, the content delivery network 354 may alsobe included within the head end 12. The content delivery network 354 maybe managed or operated by operators other than the operators of the headend 12. The content delivery network 354 may be responsible forcommunicating content to the various devices outside of the head end 12.Although only one content delivery network 354 is illustrated, multiplecontent delivery networks may be used.

The program data module 313 may be in communication with an imageprocessing module 360. The image processing module 360 may process imagedata received from a visual source as is described below. The visualsource may be located externally to the head end 12 such as at a mobileuser device, wearable device or within a vehicle connected to thein-vehicle infotainment system. The image processing module 360 isprocessed to determine unique signatures, predefined patterns orcharacteristics of an image. The image processing module 360 may be incommunication with an optical character recognition module 362. Theoptical character recognition module 362 may be used to recognize usersassociated within a vehicle using the in-vehicle infotainment system sothat user profiles may be used to personalize content, settings orprofiles. Of course the head end is only one such place to perform userdetermination.

The image processing module 360 may also be in communication with animage database 364. The image database 364 may include various imagesassociated with user identifiers. For example, the image database 364may include facial or body images of various users so recognition maytake place.

Referring now to FIG. 4A, the mobile device 34 is illustrated in furtherdetail. The mobile device 34 includes a controller 410 that includesvarious modules that control the various functions.

The controller 410 is in communication with a microphone 412 thatreceives audible signals and converts the audible signals intoelectrical signals. The audible signals may include a request signal.The request signal may be to perform a search, obtain guide data networkdata or playlist data (or content associated with a playlist). Theplaylist content may correspond to a playlist associated with a userprofile

The controller 410 is also in communication with a user interface 414.The user interface 414 may be buttons, input switches or a touch screen.

A network interface 416 is also in communication with the controller410. The network interface 416 may be used to interface with the network50. As mentioned above, the network 50 may be a wireless network or theinternet. The network interface 416 may communicate with a cellularsystem or with the internet or both. A network identifier may beattached to or associated with each communication from the mobile deviceso that a determination may be made by another device as to whether themobile device and the user receiving device are in the same local areanetwork.

The mobile device 34 may also include a visual source 418. The visualsource 418 may be a camera or charge coupled device. The visual source418 captures an image signal. The image signal may be a digital imagesignal or an analog image signal used for user recognition. Recognitionmay take place within the mobile device, the user receiving device, thewearable device or the head end.

The mobile device 34 may also include a GPS receiver 420. The GPSreceiver 420 may be used to determine a position of the mobile device asa coordinate on the Earth's surface. The GPS receiver 420 may generate alocation signal.

The controller 410 may also be in communication with the display 40described above in FIG. 1. The controller 410 may generate graphicaluser interfaces and content descriptions.

The controller 410 may also include a language processing module 430, acommand generation module 432 and a language processing module 434.Modules 430, 432 and 434 are optional components. That is, commandgeneration and language responsiveness may be performed in remotelocations such as external to the mobile device. Each of the head end12, the user receiving device 22 or the mobile device 34, and thein-vehicle infotainment system 44 may optionally include one or morelanguage processing modules, command generation modules or languageresponsiveness modules. Also, as mentioned above, none of the devicesmay include the modules. Rather, the modules may be interconnected withthe network 50 without residing in the head end, the user receivingdevice or the mobile device. Variations of this will be provided in theexample set forth below.

A recommendation engine 436 may also be included within the controller410. The recommendation engine 436 may have various data that is storedin a memory 450 of the mobile device 34. For example, selected content,content for which further data was sought, and recorded content may allbe stored within the memory 450. The recommendation engine 436 mayprovide recommendations obtained whose content data or metadata has beenobtained from the head end 12. The recommendations may be tailored tothe interests of the user of the mobile device. The recommendationengine 436 may communicate the data such as the selected content, thecontent for which data was sought, the recorded content and the like tothe head end and, in particular, the profile processing module 350.

The controller 410 may also include a gesture identification module 438that identifies gestures performed on the display 38. For example, thegestures may be a move of dragging the user's finger up, down, sidewaysor holding in a location for a predetermined amount of time. A gestureperformed at a certain screen may be translated into a particularcommand.

A profile manager 444 may store user profile data within the mobiledevice. The profile manager 444 may store user settings, such asfavorites and parental controls. The profile manager 444 may also saverelative to the recommendation engine 436 for each individual user ofthe mobile device. The profile manager 444 may also receive profile datafrom the profile processing module 350 of the head end 12 through thenetwork.

A reminder module 446 may also be included within the controller 410 ofthe mobile device 34. The reminder module 446 may be associated with atime clock or other device for generating a reminder set by a user. Thereminder module 446 may generate a screen display on the display 38 thatcorresponds to a reminder and provides various choices, such as recordor tune, to the user. The reminder may be generated based on arecommendation or recommendation list or set by a user for a specificcontent.

The controller 410 may also include an image capture module 448. Theimage capture module 448 may receive the electrical image signal fromthe visual source 418 and ultimately store the image in the memory 450.The image capture module 448 may be in communication with a patternrecognition module 452. The pattern recognition module 452 may performmany of the functions of the image processing module 360. The patternrecognition module 452 recognizes patterns or signatures from the image.The pattern recognition module 452 may, however, not ultimately processand recognize images. Rather, the pattern recognition module 452 mayrecognize patterns and unique signatures which are ultimatelycommunicated to the head end 12 for processing by the image processingmodule 360 illustrated in FIG. 3. Pattern recognition may be based onmathematical algorithms based on signal positives and relative pixelpositions within the image. The pattern recognition module 452 may notprocess or compare to image data because the amount of image data may beexcessively large and thus processing at the head end 12 may be morepractical.

The mobile device 34 may also include an audio addition module 454. Theaudio addition module 454 may be used for receiving an audio signal andadding a secondary audio signal thereto. Details of the audio additionmodule will be set forth in FIG. 4B.

A coupling detector module 456 may also be included within the mobiledevice 34. The coupling detector module 456 is used to detect thecoupling of the mobile device 34 with the in-vehicle infotainment system44. The coupling detector module 456 allows in-vehicle control of themobile devices 34 through the in-vehicle infotainment system 44. Detailsof this will be set forth below. The coupling detector module 456detects when a mobile device 34 is coupled to an in-vehicle network.

The mobile device 34 may also comprise a location display controller458. The location display controller 458 may control the display 40 ofthe mobile device 34 to display a saved location. The location displaycontroller 458 may allow the mobile device 34 to for example, detect alast location of the vehicle when the mobile device 34 is decoupled fromthe in-vehicle network.

A display suppression module 460 may also be incorporated into themobile device 34. The display suppression module 460 may be used tosuppress the display of the mobile device when the mobile device 34 iswithin the in-vehicle network. That is, when a connection with thein-vehicle infotainment system is made, a blocking signal generated atthe display suppression module prevents or suppresses a notificationsignal such as a reminder or suggestion from being displayed.Suppressing the display may include suppressing a notification at mobiledevice and thereafter communicating the notification to the in-vehicleinfotainment system so that the notification is displayed on a displayassociated therewith.

Referring now to FIG. 4B, the audio addition module 454 is illustratedin further detail. The audio addition module 454 may include an audioplayer 462. The audio player 462 is used to extract audio from atelevision signal. The television signal may be referred to as an HTTPlive streaming signal (HLS). The audio signal from the audio player 462may be communicated to an audio combiner module 464.

The audio addition module 454 may also include a second audio player466. The second audio player 466 may receive a signal, such as anadvertisement audio signal, by way of the network 50. The second audioplayer 466 receives the audio signal and communicates the audio signalto the audio combiner module 464.

The HLS stream may include a trigger signal 468. The trigger signal maybe communicated to a timing module 470. The timing module 470 maytrigger the audio player 466 to play back the second audio stream, suchas the ad or sports play description, and communicate the ad to theaudio combiner module 464. The audio player 466 may buffer the signal inan internal memory within the audio player, or a separate memory withinthe mobile device.

A text-to-speech converter 472 may be used to receive a text signalgenerated by the head end, another component of the system. As mentionedabove, the head end may generate a text signal that corresponds to thedetails of a particular play, or even an advertisement. Thetext-to-speech converter 472 converts text data to an audible signalwhich is communicated from the text-to-speech converter 472 to the audiocombiner module 464. Ultimately, the audio combiner module 464communicates content through the mobile device 34 to the in-vehicleinfotainment system 44 illustrated in FIG. 1. Details of the operationof the audio addition module will be described below.

Referring now to FIG. 5, a block diagrammatic view of wearable device 36is set forth. As mentioned above, the wearable device 36 may be one of anumber of types of wearable devices including a computerized watch orwrist worn device, a head worn device such as GOOGLE GLASS® or anothertype of computerized device suitable to be worn or affixed to the user.The wearable device 36 may include a microphone 512 that receivesaudible signals and converts the audible signals into electricalsignals. A visual source 514 such as a camera generates digital imagesignals. A touchpad 516 provides digital signals corresponding to thetouch of a hand or finger. The touchpad 516 may sense the movement of afinger or other user input. The wearable device 36 may also include amovement sensor 518 that provides signals corresponding to movement ofthe device. Physical movement of the device may also correspond to aninput. The movement sensors 518 may include accelerometers and momentsensors that generate signals that allow the device to determine therelative movement and orientation of the device.

The wearable device 36 may also include a network interface 520. Thenetwork interface 520 provides input and output signals to a wirelessnetwork, such as the internet. The network interface may alsocommunicate with a cellular system.

A Bluetooth® module 522 may send and receive Bluetooth® formattedsignals to and from the controller 510 and communicated them externallyto the wearable device 36.

An ambient light sensor 524 generates a signal corresponding to theambient light levels around the wearable device 36. The ambient lightsensor 524 generates a digital signal that corresponds to the amount ofambient light around the wearable device 36.

The controller 510 may also be in communication with the display 40 anaudio output 530 and a memory 532. The audio output 530 may generate anaudible signal through a speaker or other device. Beeps and buzzers toprovide the user with feedback may be generated. The memory 532 may beused to store various types of information including a user identifier,a user profile, a user location and user preferences. Of course, otheroperating parameters may also be stored within the memory 532.

The controller 510 may include various modules that correspond to themodules set forth in the mobile device in FIG. 4. The languageprocessing module 540, the command generation module 542, the languageresponsiveness module 546, the recommendation engine module 548, thegesture identification module 550, the profile manager module 552, thereminder module 554, the display suppression module 560, the locationdisplay controller 562, and the coupling detector module 564, correspondto the functions of the language processing module 430, the commandgeneration module 432, the language responsiveness module 534, therecommendation engine module 436, the gesture identification module 438,the profile manager module 444, the reminder module 446, the displaysuppression module 460, the location display controller 458, and thecoupling detector module 456, respectively, and of FIG. 4. The functionsof these elements will not be repeated again.

The wearable device 36 may also include an image capture module 556 anda pattern recognition module 558. The image capture module 556 may be incommunication with the visual source 514 in a similar manner to thatdescribed above relative to the corresponding modules of the mobiledevice 34 in FIG. 4. Further, the pattern recognition module 558 mayalso act in a similar manner to that set forth above with respect to thepattern recognition module 452. However, the pattern recognition module558 may be an optional component of the controller 510. That is, thecontroller 510 of the wearable device 36 may not include the patternrecognition module 558. It is envisioned that some wearable devices 36may not include a significant amount of computing power. The wearabledevice 36 may rely on an associated mobile device 34 for processing theimage signal. The pattern recognition module 452 of the mobile device 34illustrated in FIG. 4 may perform the pattern recognition module. Theimage capture module 556 may communicate a digital signal through anetwork or a network interface 520 or Bluetooth® module 522 to allow themobile device 34 to receive the signal therein. The mobile device 34 ofFIG. 4, once recognizing the image data and performing patternrecognition in the pattern recognition module 452, may communicate therecognized pattern to the head end as described above relative to FIG.4.

Referring now to FIG. 6, the in-vehicle infotainment system 44 isillustrated in block diagrammatic form. The infotainment system 44 iscontained within the vehicle 46 as described above. The vehicle 46 mayinclude various components that interact with the in-vehicleinfotainment system 44. For example, the vehicle 46 may include atransmission selector 610 that is used to select a gear of thetransmission. The transmission selector 610 may provide electronicfeedback as to the position of a transmission selector. Transmissionselectors may take many forms, including a stick shift, a PRNDL stickselector, or a push button selector. The transmission selector 610 maygenerate a transmission selector signal that is communicated to thein-vehicle infotainment system.

An on-board vehicle diagnostic data module 612 is a system that may alsocommunicate with the in-vehicle infotainment system. The OBD data module612 may obtain various types of data from the vehicle including speeddata, engine sensor data, distance or trip data, and the like.

The vehicle 46 may also include a global position system 614. The globalposition system 614 provides coordinate location data to the in-vehicleinfotainment system 44. It should be noted that the global positioningsystem 614 may also be included within the in-vehicle infotainmentsystem. A secondary display 616 may also be included within the vehicle46. The secondary display 616 may be used for displaying various typesof data. The secondary display 616 may be a standalone device, such asthe mobile device 34 or wearable device 36 described above. Thesecondary display 616 may include an antenna 618 that communicatesthrough a local area network or in an in-vehicle network.

The in-vehicle infotainment system 44 may also include an antenna 640that is in electrical communication with a Wi-Fi interface 642. Theantenna 640 may be used to communicate with an external Wi-Fi networksuch as a home Wi-Fi network. The antenna 640 may also be used to form aWi-Fi network with devices within the vehicle and thus may form anin-vehicle network.

The in-vehicle infotainment system 44 may also include a microphone 644that is used for providing an audio input to the in-vehicle infotainmentsystem 44. The microphone 644 may be used for requesting variouscommands or making VOIP calls from the in-vehicle infotainment system 44as described below. The microphone 644 may act as a user interface forreceiving voice commands.

A user interface 646 may also be incorporated into the in-vehicleinfotainment system 44 may include a touch screen, keyboard or buttons.Of course, other types of user interfaces may be incorporated into thein-vehicle infotainment system, such as the microphone 644 describedabove.

An interior camera 648 may also be incorporated into the in-vehicleinfotainment system. The interior camera 648 may be used for occupantidentification. The interior camera 648 may detect one or more occupantsso that vehicle profiles and the like may be customized. The interiorcamera 648 generates an image signal. One or more interior cameras 648may be used for occupant detection.

The in-vehicle infotainment system 44 includes a controller 660 that isused for controlling the various functions. The controller 660 mayinclude a display controller module 662 that is used to control thevarious displays associated with the infotainment system.

An occupant identifier module 664 may also be included with thein-vehicle infotainment system 44. The interior camera 648 may providean input to the occupant identifier module 664. The occupant identifiermodule 664 may adjust the profiles and detect the occupants. Theinterior camera 648 may also have its signal communicated through anetwork to another device such as the user receiving device 22 describedabove in FIG. 1.

A display setting controller 666 may be in communication with theoccupant identifier module 664. The display setting controller 666 maydetermine the settings from profile data 668 contained within a memory670. The profile data 668 may include playlists, content, displaysettings, favorites and the like. The display setting controller may setthe display to different settings based upon different occupants. Thememory 670 may also store other data including actual content, and otheroperational settings of the in-vehicle infotainment system 44.

A primary display 680, and a secondary display 682 are illustrated asbeing incorporated in the in-vehicle infotainment system. The displaysmay be wired or wirelessly connected to the controller 660. The primarydisplay 680 may be a display that is located in the front of the vehiclein the instrument panel. The secondary displays 682 may be incorporatedin a seatback or drop down screen display located within the vehicle 46.The primary display 680 may be referred to as a master or primarydisplay, in that various controls may be initiated or operated that thesecondary displays 682 cannot perform. The primary display 680 may alsobe disabled or partially disabled once the vehicle is underway. Forexample, videos may be prevented from being displayed. Determining thevehicle is underway may take place using speed data from the OBD datamodule 612 or the transmission selector signal from the transmissionselector 610. Of course, a combination of the transmission selectorsignal and OBD data may be used to determine the vehicle is underway andgenerate a disable signal at the controller. It should be noted that allthree displays 680 and the two secondary displays 682 may each beoperated independently. The displays 680, 682 may have headphone jacksor speakers associated therewith. A speaker 684 representing one or morespeakers may be included in the in-vehicle infotainment system 44. Thespeakers 684 may be dedicated to the in-vehicle infotainment system 44or may be shared with the rest of the vehicle.

The controller 660 may perform various functions, including thoseillustrated in the modules 662 through 666. The description of thevarious functions performed by the controller 660 and the interaction ofthe in-vehicle infotainment system 44 with the other devices within thein-vehicle network 686 are set forth in further detail below.

Referring now to FIG. 7, a method for resuming content being played backwithin a vehicle is set forth. The method applies equally to wearabledevices or mobile devices. In step 710, a wearable or mobile device iscoupled to an in-vehicle infotainment system. This may be performedthrough the network 686 shown in FIG. 6, or through a direct connectionsuch as a Bluetooth® connection. In step 712, content is played backthrough the in-vehicle infotainment system in a system without dedicateddisplays, the displays of the wearable or mobile devices may be used forplaying back content. In step 714, the content position is communicatedto the wearable or mobile device. This may be performed periodically,continually, or upon trigger from in-vehicle data, such as placing thevehicle in park. The content position may correspond to the lastplayback position of the content. Because of the updates being performedupdated playback positions are stored. It may be the exact position or arelatively close position to the last played position. In-vehicle datamay come from the onboard diagnostic data module 612 illustrated in FIG.6, or the transmission selector 610 of FIG. 6.

In step 718, the wearable or mobile device is disconnected from theinfotainment system. Disconnecting the wearable or mobile device fromthe infotainment system may take place when the ignition is off, or themobile or wearable device is out of range for Bluetooth or the WiFiantenna. When the wearable device is not disconnected in step 720,content continues to playback in steps 712 through 718.

In step 720, when the mobile or wearable device is disconnected, step722 generates an on-screen display for the mobile or wearable device forresuming content playback in the future. The screen by way of examplemay be referred to a resuming future playback screen which is describedin FIG. 8A. In step 724, the display is selected to generate a resumesignal with a content position. In step 724, the content positioncorresponding to a last playback position was stored within the wearableor mobile device. In step 726, the content position may be communicatedto the head end. That is, a resume future playback position, a useridentifier, and a content identifier may be communicated to the head endfor storage therein. In this manner, the content may be played back fromany device based on the stored content position. This step is anoptional step.

After step 724, step 728 may be performed. In step 728, the contentposition may be communicated to the set top box. This may be performedinstead of to the head end as described above in step 726. The contentposition may be communicated with a user identifier and a contentidentifier. In step 730, a screen display is generated at the set topbox for resuming content. In step 732, a selection or content positionrequest signal may be generated in association with the set top box, oranother user device associated with the account. In step 732, theselection signal for resuming content form the content position isgenerated. In step 736, content may be resumed from a positioncorresponding to the stored playback position.

In step 734 the content position signal may be communicated to therequesting device. The requesting device that generates the contentposition request signal may be the set top box or another mobile orwearable device.

Referring now to FIG. 8A, a screen display 810 is illustrated forresuming playback of content in the future. A message 812 on theresuming future playback screen is generated for querying whether thecontent is desired to be resumed in another location. Button 814 may bea screen display button, or may be activated by another type of userinterface at the mobile or wearable device. Button 814 corresponds to anaffirmative or “yes” position, and button 816 corresponds to a “no”position. The screen display 810 may be generated at step 722 of FIG. 7.In response to the “yes” selection, a content position signal may becommunicated to the head end or set top box.

Referring now to FIG. 8B, a screen display 830 is displayed for resumingcontent. A message 832 corresponding to resuming playback may bedisplayed to the user at another device, such as the set top box, amobile or wearable device. Message 832 may read, for example, “Thiscontent was previously viewed”. Would you like to resume playback fromthe previous position?” Selector buttons 834 and 836 may be displayed.Selector button 834 corresponds to an affirmative or “yes” decision forresuming content playback. A content position may be communicated to therequesting device when the selector button 834 is selected. By selectingselector button 836, the content will not be resumed at a previousposition.

Referring now to FIG. 9, a method for recording content at the set topbox when content is played back from an in-vehicle infotainment systemis set forth. In step 910, a mobile device is coupled to an in-vehicleinfotainment system. As mentioned above, this may take place usingBluetooth® or bringing the mobile or wearable device into the in-vehiclenetwork. This may be performed by communicating a user identifier or auser device identifier to the in-vehicle infotainment system. A passwordmay also be used. In step 912, the user identifier or device identifieris communicated to the head end. In step 914, a notification signalcomprising a reminder signal or suggestion signal is communicated fromthe head end to the mobile device. The reminder signal may be generatedin response to an established reminder set up by the user for generatinga reminder when a particular content is about to be broadcasted. Thereminder signal may be generated at various devices including the settop box, the wearable device, the mobile device or the in-vehicleinfotainment system. When the predetermined time is reached, thereminder signal may be communicated to the user at the mobile devicecurrently being operated. A suggestion signal from step 914 may also begenerated. The suggestion signal may correspond to a recommendation orrecommendation list based upon various parameters, including previouslyviewed content.

In step 916, a blocking signal may be generated at the wearable deviceor to suppress the reminder signal or suggestion signal from beingdisplayed at the wearable or mobile device. The blocking signal may begenerated in response to the mobile or wearable device being coupled tothe in-vehicle infotainment system through the in-vehicle network orthrough a direct connection, such as a Bluetooth® connection. In step918, the notification signal is communicated from the mobile device tothe in-vehicle infotainment system. In step 920 a reminder signal,recommendation signal or suggestion signal is generated at a screendisplay in the in-vehicle infotainment system. In this document,recommendation and suggestion are equivalent. In this manner, steps916-920 cooperate so that the in-vehicle infotainment system generatesthe screen display, rather than the wearable or mobile device. This willreduce operator distraction if the wearable or mobile device is for thedriver of the vehicle. In step 922, playback of the content may beperformed when selecting a “tune” button on a screen display displayingthe reminder signal. A tune selector signal is generated by selectingthe tune button. The tune selector signal may comprise a contentidentifier. The head end content delivery network may then streamcontent to the in-vehicle infotainment system. Streaming may take placedirectly to the in-vehicle infotainment system or indirectly through amobile device. The screen display, or a screen display, of thein-vehicle infotainment system may then display the content beingstreamed from the head end or another content delivery network. In step924, when the record selector button is selected at a user interface,step 926 communicates a recording selector signal to the set top box.One of the steps 922 and 924 may be performed. Of course, thenotification signal may also be ignored and no action takes place. Therecording selector signal may be communicated to the set top boxdirectly through the network, or a record request signal may becommunicated from the infotainment system, the wearable device, or theuser device to the head end through the network. A conditional accesspacket signal may be generated at the head end and communicated to theset top box to initiate recording. The record signal may be communicatedto the set top box from the head end through the satellite. Content datasuch as the time, channel, and content identifier may be communicated tothe set top box.

The wearable device may then be disconnected from the infotainmentsystem. Various reasons for disconnecting the wearable device or mobiledevice from the infotainment system may be provided, such as at the endof a trip or a passenger leaving the vehicle. After step 928, step 930generates an unblocking signal. The unblocking signal is generated atthe mobile or user device so that the system notifications may begenerated at the mobile or wearable device. In step 932, a reminder orsuggestion signal screen display may then be generated at the wearableor mobile device. After step 932, steps 934 through 938 may beperformed. Steps 934 through 938 correspond to steps 922 through 928,except that the mobile or wearable device screen display is used fordisplaying the content or initiating recording of the content. That is,in step 934, playing back the content may be selected from the screendisplay generated in step 936. If a recording button is selected in step928, a record signal is communicated to the set top box in step 938.Step 938 may be performed and may perform in a similar manner to step926, in that the record signal may be communicated directly to the settop box or may be communicated to the head end, wherein the head endgenerates a conditional access signal for recording the reminded orsuggested content.

Referring now to FIG. 10A, a screen display 1010 generated at thein-vehicle infotainment system in step 920, or at the wearable or mobiledevice in step 932, is set forth. In this example, the screen display1010 is generating a message 1012 corresponding to a particular contentthat is suggested or is being reminded. A tune selector button 1014corresponds to tuning to the content at the wearable, mobile, orin-vehicle system. In the present example, “tune” is displayed withinthe tune selector button 1014. A record button 1016 may also bedisplayed in the screen display 1010. The record button 1016 generatesthe record signal and communicates the record signal ultimately to theset top box as is indicated in steps 924 and 938.

Referring now to FIG. 10B, when the record button 1016 is selected fromFIG. 10A, a record message 1022 may be generated at a screen display1020 indicating that a record signal has been sent to the set top box.

Referring now to FIG. 10C, when the tune selector button 1014 of FIG.10A is selected, a screen display 1030 may be changed and the contentmay be streamed to the in-vehicle infotainment system, the mobile orwearable device and generated in the screen display 1030. The content1032 is displayed in the screen display. Action keys 1034 may be usedfor controlling the content. Forward, reverse, play and pause may bepart of the action keys.

Referring now to FIG. 11, a flow chart of a method for tracking avehicle using the system 10 illustrated in FIG. 1 is set forth. In step1110, the wearable or mobile device is coupled to the in-vehicleinfotainment system. This process is detailed above in that a userdevice or user identifier may be communicated to the in-vehicleinfotainment system. In step 1112, a position signal is generated from aglobal positioning system within the vehicle. As mentioned above, theglobal positioning system may be located within the in-vehicleinfotainment system, or within the vehicle. A GPS system may also belocated within the wearable or mobile device. In step 1114, anapplication such as the location application 180 of the set top box oruser receiving device 22 may be initiated. The user receiving device 22may also be but is not limited to a home media center, a set back box oran integrated gateway device. In step 1116, a current position signalmay be communicated along with a user identifier to the set top box orwearable or mobile device, initiating the location application. In step1118, a map display displaying the current position of the in-vehicleinfotainment system is generated. The display of the map may beinitiated at the set top box, wearable device, or mobile device. Thismay allow, for example, a parent to view the current position of a childwithin the vehicle while watching television at the set top box, orstreaming content to a mobile device. In step 1120, past positions mayalso be displayed at the set top box or wearable device. Past positionsfor a predetermined amount of time before the initiation of theapplication in step 1114 may also be communicated to the set top box,wearable or mobile device. Past positions may also be displayed onlyafter initiation of the application. In this manner, the system mayreceive many current positions over time. Old current positions thenbecome past positions.

In step 1122, a list of user profiles connected to the in-vehicleinfotainment system may be displayed at the display at the set top box,wearable device or mobile device. In this manner, a list of occupants inthe vehicle may thus be generated. In step 1124, a display of a cameraview from in the vehicle. The camera view may display all of theoccupants within the vehicle. In step 1126, a voice-over-IP call may beinitiated from the set top box, wearable or mobile device to thevehicle. The voice signal may be a voice-over-IP signal and communicatedthrough the network 50 described above.

After step 1112, step 1130 may communicate current position signals tothe head end associated with the user identifier. The user identifiermay be a user device identifier or some type of account identifier. Instep 1132, the current position signal and prior position signals may bestored at the head end. After step 1132, the application may beinitiated in step 1114 as described above. In this manner, the head endmay store a plurality of position signals to show positions of thevehicle. After step 1132, step 1134 generates programs or advertisementsof interest based on the position signal. The position or location ofthe vehicle may be communicated to the head end as a location signal sothat appropriate advertisements and content may be communicated to orrecommended to the user at the in-vehicle infotainment system. In step1136, the programs of interest or advertisements are displayed on thein-vehicle display. The advertisements may be banner advertisements onthe in-vehicle display. Content may be displayed after selection may beacted upon as a recommendation as described above.

Referring now to FIG. 12A, a call to a vehicle may be initiated from theset top box or mobile device. This may be performed through theapplication initiated in step 1114. A call button 1212 may be initiatedthrough the application whereby a VOIP signal may be communicated fromthe set top box to the vehicle. The microphone at the set top box mayreceive audible signals and communicate the audible signals to a VOIPsignal when the call is to be ended. A button 1214 may be activated toend the call.

Referring now to FIG. 12B, a screen display 1216 is illustrated forinitiating a call to the set top box. A call button 1218 is used forcalling the set top box from the in-vehicle infotainment system. Amicrophone may be used for receiving the audible signals in a mannersimilar to making a regular phone call through a wireless network. Thein-vehicle application may generate a VOIP signal from the audiblesignal and communicate the signal to the set top box through the network50. An end button 1220 may be selected to end the call to the set topbox.

Referring now to FIG. 13, the vehicle cameras may be displayed at ascreen display 1310 at a set top box. The display 1310 illustrates afront vehicle camera illustrating a front passenger, a screen display1314 displays a side front passenger, and a rear camera may display arear passenger.

Referring now to FIG. 14, a screen display 1410 illustrating a map withvehicle positions 1412 displayed thereon is set forth. The screendisplay 1310 may be displayed over currently playing content from theset top box. The map may be the display of the map described in steps1118 and 1120. A current position 1414 may be illustrated along with thepast positions 1416 illustrated in bold. The display data may becommunicated from the in-vehicle infotainment system to the head end ordirectly to a set top box for display. Vehicle data may include variousdata such as the amount of gas available, the state of charge of thebattery, and other data. The other data may be selected from the variouson board diagnostic data available within the vehicle. The other datamay be predetermined by the system designers. A video playing portion1422 may also display the content being viewed within the in-vehiclesystem. If more than one content is being used, multiple content may bedisplayed in the currently playing portion 1422. User identifierscorresponding to the content may also be displayed. A list of occupants1428 may also be displayed. In this example, Ben, Charlie, and Alex arein the vehicle. The occupant's position may also be displayed adjacentto their respective user identifiers (names in the present example).

Referring now to FIG. 15, a method of determining the position of avehicle from a wearable device or mobile device is set forth. In step1510, the wearable device or mobile device is coupled to the in-vehicleinfotainment system. In step 1512, the transmission selector of thevehicle is monitored at the infotainment system. A transmission selectorsignal is communicated to the in-vehicle infotainment system. In step1514, the in-vehicle infotainment system determines whether a parksignal is generated at the transmission. That is, the in-vehicleinfotainment system monitors the transmission selector signal todetermine whether the transmission selector signal is indicative of apark position. The park position may be a button position or gear shiftlever position. If the transmission selector signal is not a parksignal, then step 1512 is repeated. In step 1514 when the transmissionselector signal is a park signal, step 1516 generates a geographicposition signal from the vehicle global positioning system. In step1518, the position signal is communicated to the wearable device throughthe infotainment system in response to the transmission selector signalindicating the vehicle is in park.

The position signal is stored at the wearable device in step 1520. Thewearable device may have a screen display that may be selected todisplay the position signal in step 1522. In step 1524, the parkedposition of the vehicle is displayed.

Referring now to FIG. 16A, a screen display 1610 displays a query 1612that questions whether a parked position is to be displayed. Selectorbuttons 1614 and 1616 may be displayed. Button 1614 corresponds to anaffirmative or “yes” decision for displaying the parked position of thevehicle. Button 1616 corresponds to a “no” or negative selection fordisplaying the parked position.

Referring now to FIG. 16B, one example of a vehicle position isillustrated in screen display 1630. The screen display 1630 maycorrespond to a map indicating a building 1632 and parking spaces 1634.A street 1636 may also be displayed. Of course, various types of screendisplays may be generated as well as various types of terrain orphysical features. The vehicle position indicator 1638 indicates thevehicle position within the screen display 1630. Various types ofindicators may be used for the screen display.

A scaling button 1460 may be used to scale the map larger or smaller byselecting the plus (+) or minus (−) within the scaling button 1640.

Referring now to FIG. 17, a method for operating the in-vehicleinfotainment system using intelligent profiling is set forth. In step1710, the wearable device or mobile device, or devices, are coupled tothe in-vehicle infotainment system. In step 1712, the wearable devicesor mobile devices join the in-vehicle network. As mentioned above, thein-vehicle network may be a local area network using the in-vehicleinfotainment system as a router. In step 1714, passengers are identifiedwith voice or facial recognition. Recognition may take place within thein-vehicle system, or may take place in conjunction with the head end.User device identifiers may be communicated to the in-vehicle system tofacilitate identification. In response to identifying the passengers,step 1716 obtains a user profile or profiles based upon the wearable ormobile device identifiers and voice and/or facial recognition. In step1720, the user profiles are stored at the in-vehicle infotainmentsystem. In step 1722, a screen display is generated at the in-vehicleinfotainment system based on the user profiles. As mentioned above, thein-vehicle infotainment system may be in communication with variousnumbers of screen displays. For example, two or more screen displays maybe located in the rear seating positions, while a primary screen displayis located in the front of the vehicle.

In step 1724, it is determined whether the vehicle is out of park. Thisis determined using the transmission selector signal described above.When the vehicle is out of a parked position and potentially above apredetermined speed such as 5 miles per hour, step 1726 restricts thedriver display. The driver display may be restricted by not presentingvideo, restricting access to various buttons, or not allowing variousfeatures. In step 1724 when the vehicle is not out of a parked position,content may be selected at a passenger display. In step 1730, thecontent titles are displayed on the passenger display and are displayedat the driver display. The content itself may not be displayed, butrather the content titles and other information may be displayed at thedriver display. In step 1732, the programs are controlled at thepassenger display from the driver's display. In step 1734, variousbuttons or selectors may be used to control various aspects of thepassengers' viewing experience. The driver may choose to end the programin step 1734. This may be performed by selecting various screen displaybuttons. The driver may also change the program in step 1736. That is,another program may be selected for the passenger displays to bedisplaying. This may be useful for a parent to help a child selectanother program.

After step 1732, the audio settings may also be changed in step 1738.The audio settings may be changed by changing the volume, changing tothe use of headphones or the like.

Referring now to FIG. 18A, a representation of the display 49 associatedwith a driver display 1810 is illustrated relative to a first passengerdisplay 1812 and a second passenger display 1814. In this example, a“video restricted” message 1818 is displayed on the driver display 1810.This prevents the driver from watching video and being distracted whiledriving. As mentioned above, whether or not the vehicle is driving maybe determined by the transmission selector signal being in park or outof park.

The first passenger display 1812 is illustrated providing threedifferent menu options. The menu options may be chosen based upon theuser profile identified with the user using the first passenger display.The second passenger display 1814 is displaying a menu that includesdifferent content titles from those being displayed at the firstpassenger display 1812. The second passenger display may also beconfigured based upon a user profile. However, the second passengerdisplay 1814 may be changed based upon a second user profile. The seconduser profile is determined from identifiers from the wearable or mobiledevices, the voice recognition or visual recognition of the user of thesecond passenger display 1814 as described above in FIG. 17. In thepresent example, the first passenger display is displaying a menucorresponding to “SpongeBob®”, “Sesame Street®” and “Frozen®”. Thesecond passenger display 1814 is displaying a menu with “World Series®”,“NFL Playoffs®”, “Red Zone®” and “Big Hero 6®”.

Referring now to FIG. 18B, the screen displays 1810, 1812 and 1814 areillustrated after selection from the new display that the firstpassenger display is selected and a selection from the second passengerdisplay 1814 is selected. In this example, the first passenger display1812 is displaying “Frozen®”. The second passenger display 1814 isdisplaying “Big Hero 6®”.

In this example, the driver display 1810 illustrates a first screendisplay portion 1830 and a second screen display portion 1832corresponding to the first passenger display 1812 and the secondpassenger display 1814. The first screen display portion 1830 displays auser identifier 1834 and a content identifier 1836. In this example, thecontent identifier 1836 includes a title and a “poster” corresponding tothe movie being displayed at the first screen display 1812. A rating bar1840 may also be displayed on the display corresponding to a potentialrating. The content identifier 1836 corresponds to the content currentlybeing watched at the first screen display 1812.

The second screen display portion 1832 also displays a second useridentifier 1850, a second content identifier 1852 and the ratingsdisplay 1854.

Various control buttons such as a play button 1856, a download button1858, a headphone button 1860, a user selection button 1862, a settingadjustment button 1864 and an end button 1866 is set forth. The playbutton 1856 may be used for initiating the playback of a content at aselected user display. By selecting button 1858, content may bedownloaded to the in-vehicle infotainment system. Button 1860 may beused for changing the audio to a headphone setting. The users displayedat the driver screen display 1810 may be changed by selecting the button1862. Various audio and video settings may be changed by selecting thebutton 1864.

Referring now to FIG. 19, a method for synchronizing the in-vehicleinfotainment system with a set top box and operating the system is setforth.

In step 1910, local networks are searched at the in-vehicle infotainmentsystem. In step 1912, it is determined whether the in-vehicleinfotainment system is within range of the home network. The homenetwork connection may be established by presetting the password in thein-vehicle infotainment system. If the system is not within the homenetwork, step 1910 is again executed.

After step 1912 and the in-vehicle infotainment system is within thehome local area network, the home network is joined in step 1914. Instep 1916, a request for playback data, a user profile and user settingsis generated by the in-vehicle infotainment system in step 1916. Therequest signal in step 1916 may be for all users of the in-vehicleinfotainment system. The data may also be obtained for all past users ofthe in-vehicle infotainment system. That is, it is likely that the pastusers correspond to the users of the set top box or the like. Thus, whenstep 1916 generates a request signal for playback data, the users of theset top box within the home may be the same as the users of thein-vehicle infotainment system. In this manner, the in-vehicleinfotainment system may be kept up to date with content data. Therequest signal may include an in-vehicle infotainment system identifier,a user identifier or user identifiers. A data identifier may also becommunicated to obtain a specific type of data. The playback data fromstep 1916 may include a list of playback content as well as the actualcontent. In step 1918, the content, the bookmarks and playlists for eachuser of the in-vehicle infotainment system and the set top box withinthe home are communicating with the in-vehicle infotainment systemthrough the home network. The content may also be stored in thein-vehicle infotainment system in step 1918. In step 1920, mobile andwireless devices may be coupled to the in-vehicle infotainment system.This may be performed by communicating a device identifier from thewearable or mobile device to the in-vehicle infotainment system.

In step 1922, the various data obtained from the home system may bedisplayed. For example, content, bookmarks and a display listcorresponding to the first user device may be displayed at a firstdisplay within the in-vehicle infotainment system.

In step 1924, content may be selected for playback at the first userdevice using a selection signal and the first user device identifier. Instep 1926, a selection signal is communicated to the in-vehicleinfotainment system from the first user device. In step 1928, content iscommunicated to the first device from the in-vehicle system. Therequested content is played back at the first user device in step 1930.A position signal may be communicated to the in-vehicle system in step1932. The position signal may be communicated to the head end in step1934. By communicating the position signal, the position of the contentmay ultimately be saved and used to resume content at another device sothat playback may resume at or near the position left off in thein-vehicle system. It should be noted that wearable devices, mobiledevices and in-vehicle screens may be used for requesting content andplaying back content within the in-vehicle network.

Referring back to step 1922, content may be displayed at a second userdevice within the in-vehicle system in step 1940. The second content,second bookmarks and second playlists may all be displayed, which aredifferent than those displayed in step 1922. However, some of theelements within the lists may be the same. In step 1942, contentselection for the second user device may be selected for playback. Instep 1944 the selection signal may be communicated to the in-vehiclesystem through the in-vehicle network. In step 1946, content may becommunicated to the second device within the in-vehicle infotainmentsystem. Steps 1948 through 1952 correspond directly to steps 1930through 1934, except that the content is played back at the second userdevice and the position signal corresponds to the position of the secondcontent.

Referring now to FIG. 20, a screen display 2010 illustrating contentposters 2012 corresponding to content stored within the in-vehicleinfotainment system is set forth. In this example, the posters 2012correspond to content corresponding to a first user of the in-vehicleinfotainment system. It should be noted that the content may becommunicated from a set top box, a home media center or a gateway.

Referring now to FIG. 21, a method for displaying different portions ofthe same content signal is set forth. In step 2110, a first device andsecond device are coupled to the in-vehicle infotainment system throughan in-vehicle network. The system may include dedicated displaysprovided within the in-vehicle system or may include devices such as awearable device or mobile device that are brought in to the in-vehiclenetwork.

In step 2112, content is selected for playback from a screen display.The screen display may be one of the screen displays associated with thein-vehicle system or from a mobile or wearable device. A screen displaymay list a plurality of content therein. In step 2114, selecting a “joydrive” button to form a signal separation selection signal may beperformed. By selecting signal separation, portions of the signal suchas the audio portion and a data portion may be separated and displayedon separate parts of the screen as will be described below. By forming asignal separation selection signal, the in-vehicle infotainment systemmay allow a karaoke-type playback for content. That is, one user mayview the lyrics of the song while another user views a video without thelyrics. Both of these displays may generate the music while the lyricsmay be sung by an occupant.

In step 2116, a first portion of the signal is communicated to a firstuser device or display through the in-vehicle network. In step 2118, asecond portion of the first content signal is communicated to a seconduser device through the in-vehicle network. In step 2120, a thirdportion of the first content signal is communicated to the first userdevice or display and the second user device or display through thein-vehicle network. This may, for example, correspond to the music of asong-based content. In step 2122, the first portion of the content andthe third portion are displayed at the first display. In step 2124, thesecond portion and the third portion are displayed at the seconddisplay.

Referring now to FIG. 22, a first screen display 2210 is illustratedhaving a plurality of content displayed thereon. Upon selection of oneof the content in the list, a window 2216 may be generated. The window2216 may correspond to a “joy drive” selection button used for selectinga karaoke-type display of the content. In this example, “Sonictap®” is amusic station for broadcasting music. The signal from the music stationmay include lyrics and/or a video. A first screen display 2220 displaysthe lyrics associated with the content selected. A second screen display2222 displays a video without the lyrics corresponding to the contentselected. Of course, the lyrics may be displayed over the video itself.However, the lyrics are not displayed on both displays 2220 and 2222.

Referring now to FIG. 23, a method of providing audible signals to anin-vehicle infotainment system is set forth. The method set forth inFIG. 23 may be used for providing the audio signals or enhanced audiosignals to be audibly displayed through the in-vehicle infotainmentsystem. In step 2310, an application is initiated at a mobile device. Instep 2312, controls may be displayed at the mobile device and at thein-vehicle infotainment system. In step 2314, the audio stream isextracted from an audio-video source signal. In step 2316, the firstaudio stream is received at the mobile device from the extractedaudio-video source signal. In step 2318, the first audio stream may beplayed back from the first audio player within the application. In step2320, the first audio stream is communicated to the in-vehicleinfotainment system. In step 2322, a second audio stream is received.The second audio stream may be received from various sources includingfrom a secondary website. The second audio stream may be anadvertisement signal or, as set forth in steps 2324 and 2326, from atext signal. In step 2324, the text signal may be received through theapplication. The text signal corresponds to an eventually formed audiostream. In the present example, the text signal may correspond to adescription of a key play in a football game, for example. In step 2326,a trigger for the second audio stream may be received. The trigger maybe received as part of the first audio signal, or may be received from asecondary source such as the content head end. In step 2328, the secondaudio stream is played back over the first audio stream so that bothaudio streams are communicated to the in-vehicle infotainment system asin step 2330. Communication in step 2330 may take place throughBluetooth® or through a physical wire coupling. Communication throughthe in-vehicle network may also take place since the mobile device maybe in a local area network with the in-vehicle system. In step 2332,both the first audio stream and the second audio stream aresimultaneously played back through the in-vehicle infotainment system.

Referring now to FIG. 24, a mobile device 2410 is illustrated having ascreen display 2412 corresponding to the user interface of anapplication. The application may detect when the mobile device 2410 isin the presence of an in-vehicle network. The screen display 2412 maydisplay various sports scores 2414 for various games, such as NFL®games. A screen display 2420 of the in-vehicle infotainment system isillustrated coupled to the mobile device 2410 through a connection 2416.The connection 2416 may take place through the in-vehicle network (wiredor wireless) or through Bluetooth® (or another localized communicationformat). The in-vehicle display 2420 displays a game title or programtitle 2422 for a game being communicated through the mobile device 2410.That is, the title 2422 corresponds to the title being streamed from themobile device. As mentioned above, the mobile device 2410 may separatethe audio and video streams so that the audio stream is communicatedthrough the in-vehicle infotainment system. A control panel 2424 is usedfor controlling the audio stream. A playback button 2426, a forwardbutton 2428 and a reverse button 2430 may be used. A tune button 2434may be used to tune to different audio streams that may be providedthrough the mobile user device. A second control panel 2440 may be usedto control other functions of the in-vehicle infotainment system.

Those skilled in the art can now appreciate from the foregoingdescription that the broad teachings of the disclosure can beimplemented in a variety of forms. Therefore, while this disclosureincludes particular examples, the true scope of the disclosure shouldnot be so limited since other modifications will become apparent to theskilled practitioner upon a study of the drawings, the specification andthe following claims.

What is claimed is:
 1. A method comprising: coupling a mobile devicehaving an identifier to an in-vehicle infotainment system; generating avehicle position signal for a vehicle; communicating the identifier andthe vehicle position signal corresponding to a current vehicle positionto a user device, the user device separate from the mobile device andthe in-vehicle infotainment system, the user device controllable byinputs from a user through a user interface display associated with auser interface; generating a map display at the user device, the mapdisplay displaying a map comprising a representation of the vehicle atthe current vehicle position and the identifier of the mobile device;the method further comprising receiving, at the in-vehicle infotainmentsystem, advertisement signals from an advertisement source through thehead end.
 2. The method of claim 1 wherein the user device comprises aset top box.
 3. The method of claim 1 wherein generating the map displaycomprises generating the map display comprising the current vehicleposition and a past vehicle positions on the map display.
 4. The methodof claim 1 wherein coupling the mobile device comprises coupling aplurality of mobile devices, each comprising respective identifiers andfurther comprising displaying the respective identifiers on the mapdisplay.
 5. The method of claim 1 wherein communicating the vehicleposition signal comprises communicating the identifier and the vehicleposition signal to the user device through a head end.
 6. The method ofclaim 1 further comprising generating a recommendation list comprisingat least one recommendation determined in response to the vehicleposition signal.
 7. The method of claim 1 wherein generating the mapdisplay comprises generating the map display as an overlay to a contentsignal generated by the user device.
 8. The method of claim 1 furthercomprising communicating a voice-over-IP signal from the user device tothe in-vehicle infotainment system.
 9. The method of claim 1 furthercomprising communicating a voice-over-IP signal from the in-vehicleinfotainment system to the user device.
 10. The method of claim 7further comprising communicating advertisement signals to the in-vehicleinfotainment system from an advertisement source.
 11. The method ofclaim 1 further comprising communicating vehicle data to the in-vehicleinfotainment system and displaying vehicle data at the map display. 12.A system comprising: a mobile device having a mobile device identifierassociated therewith; an in-vehicle infotainment system; the mobiledevice communicating the mobile device identifier to the in-vehicleinfotainment system; a user device coupled to the in-vehicleinfotainment system of a vehicle, the user device controllable by inputsfrom a user though a user interface display associated with the userinterface; a global positioning system generating a vehicle positionsignal at the vehicle, said user device separate from the in-vehicleinfotainment system and the global positioning system; the in-vehicleinfotainment system communicating the vehicle position signalcorresponding to a current vehicle position and the mobile deviceidentifier to the user device; and the user device is associated with adisplay displaying a map display comprising a map with a representationof the vehicle at the current vehicle position and the mobile deviceidentifier of the mobile device; the system further comprising a headend which communicates advertisement signals to the in-vehicleinfotainment system from an advertisement source.
 13. The system ofclaim 12 wherein the user device comprises a set top box.
 14. The systemof claim 12 wherein the user device generates the map display comprisingthe current vehicle position and a past vehicle position on the mapdisplay.
 15. The system of claim 12 wherein the mobile device comprisesa plurality of mobile devices, each of the mobile devices comprisingrespective identifiers and wherein the display displays the respectiveidentifiers.
 16. The system of claim 12 further comprising anadvertisement source communicating advertisement signals to thein-vehicle infotainment system based on the vehicle position signal. 17.The system of claim 12 further comprising a vehicle diagnostic systemcommunicating vehicle data to the in-vehicle infotainment system andwherein the display of the user device displays the vehicle data.
 18. Amethod comprising: coupling a mobile device having an identifier to anin-vehicle infotainment system; generating a vehicle position signal ata vehicle; communicating the vehicle position signal corresponding to acurrent vehicle position to a user device set top box, the set top boxseparate from the mobile device and the in-vehicle infotainment system,the set top box controllable by inputs from a user though a userinterface display associated with the user interface; communicating theidentifier to the user device set top box from the in-vehicleinfotainment system; and enabling the set top box user device togenerate a map display comprising a representation of the vehicle at thecurrent vehicle position and the identifier of the mobile device.